On Sun, 2012-06-03 at 14:56 +0100, Ben Hutchings wrote:
> On Sun, 2012-06-03 at 01:50 -0500, Jonathan Nieder wrote:
> > Ben Hutchings wrote:
> >
> > > We would certainly like to do this, but we want to find a way to do so
> > > while properly tracking bugs that may apply to both the old 'linux-2.6
On Sun, 2012-06-03 at 01:50 -0500, Jonathan Nieder wrote:
> Ben Hutchings wrote:
>
> > We would certainly like to do this, but we want to find a way to do so
> > while properly tracking bugs that may apply to both the old 'linux-2.6'
> > and the new 'linux'.
>
> Based on experience of the git-cor
Ben Hutchings wrote:
> We would certainly like to do this, but we want to find a way to do so
> while properly tracking bugs that may apply to both the old 'linux-2.6'
> and the new 'linux'.
Based on experience of the git-core -> git renaming:
The only downside I know of is that you have to look
On Sat, 2011-07-30 at 10:14 +0200, Clara Gnos wrote:
> Package: linux-2.6
> Severity: wishlist
>
> To use the name linux-2.6 for the source package is quite misleading. Maybe
> it
> is better to drop this -2.6 appendix and use the name linux as Linus Torvalds
> does since the release of 3.0 [1]
Package: linux-2.6
Severity: wishlist
To use the name linux-2.6 for the source package is quite misleading. Maybe it
is better to drop this -2.6 appendix and use the name linux as Linus Torvalds
does since the release of 3.0 [1].
[1] https://lkml.org/lkml/2011/7/20/371
--- System information.
5 matches
Mail list logo
