public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed

From: Junio C Hamano <gitster@pobox•com>
To: Jeff King <peff@peff•net>
Cc: git@vger•kernel.org
Subject: Re: [RFH] hackday and GSoC topic suggestions
Date: Tue, 11 Feb 2014 10:57:22 -0800	[thread overview]
Message-ID: <xmqq1tz9qxyl.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20140205225702.GA12589@sigill.intra.peff.net> (Jeff King's message of "Wed, 5 Feb 2014 17:57:02 -0500")

Jeff King <peff@peff•net> writes:

>  - Branch rename breaks local downstream branches
>    http://article.gmane.org/gmane.comp.version-control.git/241228

If you have a branch B that builds on A, if you are renaming A to C,
you may want B to automatically set to build on C in some cases, and
in other cases your renaming A is done explicitly in order to severe
the tie between A and B and setting the latter to build on C can be
a bad thing---after all, the user's intention may be to create a
branch A starting at some commit immediately after this rename so
that B will keep building on that updated A.

So I am not sure if this is a bug.

>  - git stash doesn't use --index as default
>    http://article.gmane.org/gmane.comp.version-control.git/235892

I tend to think "git stash" was designed to work this way from day
one.

>  - using git commit-tree with "-F -" adds trailing newlines
>    http://article.gmane.org/gmane.comp.version-control.git/236583

According to the initial commit that introduced this option, it
deliberately calls strbuf_complete_line() to make sure we do not
leave an incomplete line at the end.


Many of the other items in your "bugs" section seem to be worth
fixing.

Thanks.

next prev parent reply	other threads:[~2014-02-11 18:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-05 22:57 [RFH] hackday and GSoC topic suggestions Jeff King
2014-02-06  9:10 ` Christian Couder
2014-02-06  9:51   ` Matthieu Moy
2014-02-13  8:50     ` Jeff King
2014-02-13  9:28       ` Christian Couder
2014-02-13  9:55         ` David Kastrup
2014-02-08 18:43 ` Thomas Rast
2014-02-08 18:55   ` Jeff King
2014-02-08 19:03 ` Thomas Rast
2014-02-16 14:42   ` Duy Nguyen
2014-02-16 15:29     ` Thomas Rast
2014-02-11 18:57 ` Junio C Hamano [this message]
2014-02-11 19:38   ` Junio C Hamano
2014-02-13  8:37     ` Jeff King
2014-02-13  8:41   ` Jeff King

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqq1tz9qxyl.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox$(echo .)com \
    --cc=git@vger$(echo .)kernel.org \
    --cc=peff@peff$(echo .)net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox