git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [RFC/PATCHv2 1/3] Documentation/git-svn: Promote the use of --prefix in docs + examples

From
Johan Herland <johan@herland.net>
Date
Oct 6, 2013, 13:46 UTC
Message-ID
<CALKQrgdruayiosT1nQSXGn44T4dGbjNYquuq5tZjyiNSQNd6rw@mail.gmail.com>
In-Reply-To
<1B588C9FE7614A6080C98FD340530DA5@PhilipOakley>
On Sun, Oct 6, 2013 at 11:51 AM, Philip Oakley <philipoakley@iee.org> wrote:
Show 5 quoted lines
> From: "Johan Herland" <johan@herland.net>
>> Cc: Eric Wong <normalperson@yhbt.net>
>
> Excuse my ignorance, but what is the "Carbon copy:" line meant to signify?
> Should it be a double "Signed-of-by:" or one of the other "-by:" lines?

No, it's not a Signed-off-by, it's merely a hint to someone that they might want to take a closer look at this patch.

In this case, I'm Cc-ing Eric Wong, as he is the main git-svn author, and I consider his feedback on these patches very valuable. When I add a Cc: to the commit message, git send-email picks it up, and adds him to the Cc-list of the resulting email. I could have achieved the same by passing --cc "Eric ..." directly to git-send-email, but sometimes there might be quite a while between preparing the commit and running git send-email, and in those cases adding the Cc to the commit message saves me from forgetting to Cc him when I some time later get around to running git send-email.

That said, my hope is obviously that Eric will have the
time/energy/motivation to review these patches, so that I (or someone
else) can later replace the "Cc:" line with a corresponding
"Reviewed-by:" or "Acked-by:". Even if that does not happen, and the
"Cc:" line ends up in the recorded history of Git, I don't consider
that a big problem either; a 'git log origin/master | grep "^\s*Cc: "
| wc -l' yields 148 existing cases...
Hope that helps,
...Johan
-- 
Johan Herland, <johan@herland.net>
www.herland.net
Previous: Philip OakleyNext: Eric Sunshine
Message 13 of 23 in “git-svn: Use prefix by default?”
  1. Thomas Ferris NicolaisenAug 22, 2013
  2. Johan HerlandSep 30, 2013
  3. git svn: Set default --prefix='origin/' if --prefix is not givenJohan Herland, Sep 30, 2013
  4. Eric WongOct 1, 2013
  5. Johan HerlandOct 1, 2013
  6. Eric WongOct 3, 2013
  7. 1/3 Documentation/git-svn: Promote the use of --prefix in docs + examplesJohan Herland, Oct 5, 2013
  8. 2/3 git-svn: Warn about changing default for --prefix in Git v2.0Johan Herland, Oct 5, 2013
  9. Eric SunshineOct 9, 2013
  10. Johan HerlandOct 9, 2013
  11. 3/3 Git 2.0: git svn: Set default --prefix='origin/' if --prefix is not givenJohan Herland, Oct 5, 2013
  12. Philip OakleyOct 6, 2013
  13. Johan HerlandOct 6, 2013
  14. Eric SunshineOct 9, 2013
  15. Johan HerlandOct 9, 2013
  16. 0/3 Change git-svn's default --prefix in Git v2.0Johan Herland, Oct 11, 2013
  17. 1/3 Documentation/git-svn: Promote the use of --prefix in docs + examplesJohan Herland, Oct 11, 2013
  18. 2/3 git-svn: Warn about changing default for --prefix in Git v2.0Johan Herland, Oct 11, 2013
  19. Eric WongOct 12, 2013
  20. 3/3 Git 2.0: git svn: Set default --prefix='origin/' if --prefix is not givenJohan Herland, Oct 11, 2013
  21. Eric WongApr 19, 2014
  22. git-svn.txt: Retain a description og pre-v2.0 default prefixJohan Herland, Apr 19, 2014
  23. Eric WongApr 19, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.