'Comma in -to/-cc entry' on valid addresses

2015-12-16 Thread Andy Lutomirski
$ git send-email --to='"Address, Valid" ' Comma in --to entry: "Address, Valid" ' $ git --version git version 2.5.0 This appears to be a recent regression. For an authority on why the current behavior is wrong, see RFC 2822 section 3.4, which defines mailbox and mailbox-list as well as section 3.

Feature request: git bisect merge to usable base

2015-12-30 Thread Andy Lutomirski
Hi- I'm currently bisecting a Linux bug on my laptop. The starting good commit is v4.4-rc3 and the starting bad commit is v4.4-rc7. Unfortunately, anything much older than v4.4-rc3 doesn't boot at all. I'd like to say: $ git bisect merge-to v4.4-rc3 or similar. The effect would be that, rathe

Re: Feature request: git bisect merge to usable base

2016-01-04 Thread Andy Lutomirski
On Wed, Dec 30, 2015 at 12:09 PM, Junio C Hamano wrote: > Andy Lutomirski writes: > >> I'm currently bisecting a Linux bug on my laptop. The starting good >> commit is v4.4-rc3 and the starting bad commit is v4.4-rc7. >> Unfortunately, anything much older than

Re: Feature request: git bisect merge to usable base

2016-01-04 Thread Andy Lutomirski
On Mon, Jan 4, 2016 at 12:31 PM, Junio C Hamano wrote: > Andy Lutomirski writes: > >> git bisect run is great, but it's not so great when the test process >> is "sudo make modules_install && sudo make install && reboot", then >> boot new

Verifiable git archives?

2014-01-08 Thread Andy Lutomirski
It's possible, in principle, to shove enough metadata into the output of 'git archive' to allow anyone to verify (without cloning the repo) to verify that the archive is a correct copy of a given commit. Would this be considered a useful feature? Presumably there would be a 'git untar' command th

Re: Verifiable git archives?

2014-01-09 Thread Andy Lutomirski
On Thu, Jan 9, 2014 at 12:11 PM, Junio C Hamano wrote: > Andy Lutomirski writes: > >> It's possible, in principle, to shove enough metadata into the output >> of 'git archive' to allow anyone to verify (without cloning the repo) >> to verify that the arch

Re: Verifiable git archives?

2014-01-09 Thread Andy Lutomirski
On Thu, Jan 9, 2014 at 2:46 PM, Junio C Hamano wrote: > Andy Lutomirski writes: > >>> You only need the object name of the top-level tree. After "untar" >>> the archive into an empty directory, make it a new repository and >>> "git add . &&am

Re: Verifiable git archives?

2014-01-25 Thread Andy Lutomirski
Here's a rather hackish implementation of the write side. Any thoughts on the format? (Obviously the implementation needs work. For example, it needs to be optional. Thoughts so far: - I want to put the value of "prefix" into an extended header. - Should blobs have their sha1 hashes in an exte