From: Dany <nessup@gmail.com>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Feature request:
Date: Wed, 3 Jul 2013 16:53:18 -0700 [thread overview]
Message-ID: <686269E5-8539-42F9-B0B6-D7CA996A4FF2@gmail.com> (raw)
In-Reply-To: <67824DCD-A486-476D-9A04-D18B083DB090@gmail.com>
lol, confusion abound. this message was intended to be in response to "Re: Feature request: prevent push -f from pushing all branches at once"
On Jul 3, 2013, at 4:52 PM, Dany <nessup@gmail.com> wrote:
> Hey Jonathan,
>
> Thanks for the quick reply. I think that's a great message; I do have to say that I wouldn't have known what the `matching` and `simple` modes are without that message; I just had to look it up is all. It may be helpful to tell users that `simple` is probably what they want :)
>
> @DanyJoumaa
> 1 520 991 5001
>
> On Jul 3, 2013, at 4:46 PM, Jakub Narebski <jnareb@gmail.com> wrote:
>
>> [I'm sorry about breaking Cc: chain - responding via GMane web interface]
>>
>> Junio C Hamano <gitster <at> pobox.com> writes:
>>> Ed Hutchins <eh <at> demeterr.com> writes:
>>>
>>>> I'm not trying to change the way git does things (which works perfectly
>>>> well), I'm asking for some extra information to be added to the commit
>>>> so that analysis of the ancestry graph can be tied to the branch topics
>>>> that the original author was working from. [...]
>> [...]
>>> It is not just misleading but is actively wrong to recording the
>>> name of the original branch in commits and carrying them forward via
>>> rebase. If you want a record of what a group of commits were about,
>>> the right time to do so is when you merge.
>> [...]
>>
>> There is even git-resurrect.sh script in 'contrib/' that makes
>> use of that practice to find merged-in and deleted branches,
>> and resurrect them (among other tools).
>>
>> --
>> Jakub Narębski
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe git" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2013-07-03 23:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-02 19:37 Feature request: "author branch" in commit object Ed Hutchins
2013-07-02 19:49 ` Fredrik Gustafsson
2013-07-02 20:00 ` Junio C Hamano
2013-07-02 20:34 ` Ed Hutchins
2013-07-03 16:16 ` Antoine Pelisse
2013-07-03 17:31 ` Ed Hutchins
2013-07-03 18:19 ` Junio C Hamano
2013-07-04 0:00 ` Andrew Ardill
2013-07-02 20:31 ` Johan Herland
2013-07-03 9:33 ` Matthieu Moy
2013-07-03 15:47 ` Ed Hutchins
2013-07-03 18:08 ` Junio C Hamano
2013-07-03 23:46 ` Feature request: Jakub Narebski
2013-07-03 23:52 ` Dany
2013-07-03 23:53 ` Dany [this message]
2013-07-04 8:08 ` Matthieu Moy
2013-07-09 21:46 ` Feature request: "author branch" in commit object Philip Oakley
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=686269E5-8539-42F9-B0B6-D7CA996A4FF2@gmail.com \
--to=nessup@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).