Re: GIT and the current -stable

Please don't do this. Using the same name for a branch as for a tag is
madness. Call it "v2.6.20-stable" or anything else, but don't re-use the
same naming as for tags.


Yes I have done this before, and it took me awhile to realize what was
going on.  It caused me some grief, and a few hours of lost time...Of
course this was back in my earlier days ;)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

References:
- GIT and the current -stable
  - From: Rene Herman <[email protected]>
- Re: GIT and the current -stable
  - From: Junio C Hamano <[email protected]>
- Re: GIT and the current -stable
  - From: Linus Torvalds <[email protected]>

Prev by Date: Re: [Announce] [patch] Modular Scheduler Core and Completely Fair Scheduler [CFS]
Next by Date: Re: [Announce] [patch] Modular Scheduler Core and Completely Fair Scheduler [CFS]
Previous by thread: Re: GIT and the current -stable
Next by thread: Re: GIT and the current -stable
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]