Johannes Schindelin [off-list ref] writes:
On Tue, 22 Jul 2008, Tony Luck wrote:
quoted
git tag | grep next- | sort | while read tag
This should not be necessary... AFAICT "git tag" sorts its output already.
quoted
What does the "git-where-did-this-tag-branch-from-linus" command look like?
git merge-base --all <branch1> <branch2>
Be warned: there might be multiple merge bases.
I do not think that approach applies to linux-next, which is constantly
rewound to the then-tip-of-linus and merge remaining bits. The question
is "where does this branch begin", which does not have an answer in git.
quoted
git merge-base --all <branch1> <branch2>
Be warned: there might be multiple merge bases.
I do not think that approach applies to linux-next, which is constantly
rewound to the then-tip-of-linus and merge remaining bits. The question
is "where does this branch begin", which does not have an answer in git.
Using git merge-base on the next-20080701 tag and current Linus tree I get
76 possible merge bases. None of them appear to be the "right" one (if
I check out this tag and look at Next/merge.log the right answer appears
to be 1702b52 if I'm reading the log correctly).
Perhaps my best hope is to
$ git checkout $tag Next/merge.log
... parse merge.log to figure out $base ...
-Tony
Hi,
On Tue, 22 Jul 2008, Junio C Hamano wrote:
Johannes Schindelin [off-list ref] writes:
quoted
On Tue, 22 Jul 2008, Tony Luck wrote:
quoted
git tag | grep next- | sort | while read tag
This should not be necessary... AFAICT "git tag" sorts its output already.
quoted
What does the "git-where-did-this-tag-branch-from-linus" command look like?
git merge-base --all <branch1> <branch2>
Be warned: there might be multiple merge bases.
I do not think that approach applies to linux-next, which is constantly
rewound to the then-tip-of-linus and merge remaining bits. The question
is "where does this branch begin", which does not have an answer in git.
Oh.
Well, there is one thing that _could_ work most of the time, namely
looking at the committer info of the first parent.
Dunno,
Dscho
On Tue, 2008-07-22 at 10:04 -0700, Junio C Hamano wrote:
Johannes Schindelin [off-list ref] writes:
quoted
On Tue, 22 Jul 2008, Tony Luck wrote:
quoted
git tag | grep next- | sort | while read tag
This should not be necessary... AFAICT "git tag" sorts its output already.
quoted
What does the "git-where-did-this-tag-branch-from-linus" command look like?
git merge-base --all <branch1> <branch2>
Be warned: there might be multiple merge bases.
I do not think that approach applies to linux-next, which is constantly
rewound to the then-tip-of-linus and merge remaining bits. The question
is "where does this branch begin", which does not have an answer in git.
I thought that was what Stephen has the next/stable branch for:
git log --pretty=oneline --no-merges next/stable..next/master | wc -l
At least for each day you can find the number of patches....I don't
think he tags the stable points, so historically that may be a problem.
Harvey