Re: Feature request: git bisect merge to usable base

On Mon, Jan 4, 2016 at 12:31 PM, Junio C Hamano <gits...@pobox.com> wrote: > Andy Lutomirski <l...@amacapital.net> writes: > >> git bisect run is great, but it's not so great when the test process >> is "sudo make modules_install && sudo make install &a

Re: Feature request: git bisect merge to usable base

On Wed, Dec 30, 2015 at 12:09 PM, Junio C Hamano <gits...@pobox.com> wrote: > Andy Lutomirski <l...@kernel.org> 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. >>

Feature request: git bisect merge to usable base

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,

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

$ 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

Re: Verifiable git archives?

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

Re: Verifiable git archives?

On Thu, Jan 9, 2014 at 12:11 PM, Junio C Hamano gits...@pobox.com wrote: Andy Lutomirski l...@amacapital.net 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 archive

Re: Verifiable git archives?

On Thu, Jan 9, 2014 at 2:46 PM, Junio C Hamano gits...@pobox.com wrote: Andy Lutomirski l...@amacapital.net 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 . git write-tree---the result should

Verifiable git archives?

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