Re: git guidance

On Fri, 07 Dec 2007 22:04:48 +0300, Al Boldi said:

> Because WORKFLOW C is transparent, it won't affect other workflows.  So you 
> could still use your normal WORKFLOW B in addition to WORKFLOW C, gaining an 
> additional level of version control detail at no extra cost other than the 
> git-engine scratch repository overhead.
> 
> BTW, is git efficient enough to handle WORKFLOW C?

Imagine the number of commits a 'make clean; make' will do in a kernel tree, as
it commits all those .o files... :)

Attachment: pgpbxACVezu5B.pgp
Description: PGP signature

---

• Follow-Ups:
  • Re: git guidance
    • From: Al Boldi <[email protected]>
  • Re: git guidance
    • From: Luke Lu <[email protected]>

• References:
  • Re: git guidance
    • From: Jing Xue <[email protected]>
  • Re: git guidance
    • From: Al Boldi <[email protected]>
  • Re: git guidance
    • From: Jakub Narebski <[email protected]>
  • Re: git guidance
    • From: Al Boldi <[email protected]>

• Prev by Date: Re: 2.6.24-rc3-git4 NFS crossmnt regression
• Next by Date: Re: [BUG] 2.6.23-rc3 can't see sd partitions on Alpha
• Previous by thread: Re: git guidance
• Next by thread: Re: git guidance
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]