On Sat, Feb 06, 2016 at 02:23:11PM +0100, René Scharfe wrote:
> Am 28.01.2016 um 00:45 schrieb f...@fuz.su:
> >>There is git get-tar-commit-id, which prints the commit ID if it
> >>finds a comment entry which looks like a hexadecimal SHA-1 hash.
> >>It's better than a hex editor at least. :)
> >
>
Hello,
> > > Users can always go back to the original format. At least I don't
> > > expect this new format becoming the default too quickly.
>
> This is the most crucial issue here, as far as I am concerned: there are
> already tons of .zip files out there that were created by git archive, and
Hallo René,
On Wed, Jan 27, 2016 at 09:31:15PM +0100, René Scharfe wrote:
> Hello Robert,
>
> it's customary to discuss in the open by copying the list. Unless
> there are secrets involved, but I don't see any below. I kept it
> private anyway in case I missed any, but please cc:
>
On Tue, Jan 26, 2016 at 11:06:25PM +0100, René Scharfe wrote:
> Am 24.01.2016 um 16:59 schrieb f...@fuz.su:
> >Right now, git archive creates a pax global header of the form
> >
> > comment=57ca140635bf157354124e4e4b3c8e1bde2832f1
> >
> >in tar archives it creates. This is suboptimal as as
Right now, git archive creates a pax global header of the form
comment=57ca140635bf157354124e4e4b3c8e1bde2832f1
in tar archives it creates. This is suboptimal as as comments are
specified to be ignored by extraction software. It is impossible to
find out in an automatic way (short of
Hello!
I've tried to changing the URL of a remote temporarily because of network
issues. I tried something like this:
git -c remote.foo.url=http://gitserver.example/repo.git push foo bar
Tracing shows that git push does not use the provided URL for the remote foo
and instead uses the URL
6 matches
Mail list logo
