Control: forwarded -1 git@vger.kernel.org
On Fri, 2016-01-29 at 21:05 +0700, Duy Nguyen wrote:
> On Fri, Jan 29, 2016 at 8:35 PM, Ben Hutchings wrote:
> > git keeps trying to do a background gc on my linux repository, but
> > fails, reporting this in .git/gc.log:
> >
>
erges,
[...]
Each *stable update* series is a single branch made up almost entirely
of cherry-picked commits, possibly managed as a quilt series before
being reviewed and then committed. Tags are signed, and each commit has
a reference to the original (though the format of that reference isn't
well standardised).
Although Greg owns the linux-stable.git repository, several stable
updates series and the corresponding branches are maintained by others,
such as Paul and myself. When Greg pulls from them, he's mirroring the
other maintainer's branch and never merging with anyone else's work. So
it should always be a fast-forward merge. Further, the head of the
branch is always going to have a tag signed by the respective
maintainer.
Ben.
--
Ben Hutchings
Experience is what causes a person to make new mistakes instead of old ones.
signature.asc
Description: This is a digitally signed message part
;t) know anything about ordering of
tag names, but I think that if one of the containing tags is the
ancestor of all the others then 'git describe --contains' should prefer
to use that. Or at least, there should be some way to request that
behaviour.
For now, if in doubt, 'git tag --contains' will tell you all the
containing tags.
Ben.
> > And people have reported the regressions to prove it ;-)
>
> Ok, fair enough, I'll apply it.
--
Ben Hutchings
I say we take off; nuke the site from orbit. It's the only way to be sure.
signature.asc
Description: This is a digitally signed message part
3 matches
Mail list logo
