>
> What is our policy concerning deleting branches from the trac repositories
> (e.g., I usually delete all branches on trac which are merged in a stable
> release, say, just to unclutter the name space there)?
>
> The current workflow (replacing the branch by the commit id when closing
> the
Am 2014-11-16 um 12:27 schrieb Volker Braun:
> On Sunday, November 16, 2014 6:34:56 AM UTC, Clemens Heuberger wrote:
>
> > Works for me, possibly because I have a newer git.
> Can it be that it works for you because the commit
> ec0aae9358f5204a3db6406b2c2f2818a78f5892 (this is the act
On Sunday, November 16, 2014 6:34:56 AM UTC, Clemens Heuberger wrote:
>
> > Works for me, possibly because I have a newer git.
> Can it be that it works for you because the commit
> ec0aae9358f5204a3db6406b2c2f2818a78f5892 (this is the actual commit of
> #16747)
> is contained in your local rep
Am 2014-11-15 um 19:29 schrieb Volker Braun:
> Works for me, possibly because I have a newer git.
$ git --version
git version 2.1.3
Can it be that it works for you because the commit
ec0aae9358f5204a3db6406b2c2f2818a78f5892 (this is the actual commit of #16747)
is contained in your local reposito
Probably works:
git remote update trac && git trac checkout 16747
The issue is that git does not let you checkout individual sha1's, they
might have been part of a branch that has been removed intentionally (e.g.
somebody accidentally checked in their password etc).
On Saturday, November 15, 2
