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

Re: [PATCH v2 0/2] improve-wincred-compatibility

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 25, 2013, 23:51 UTC
Message-ID
<7vip5gne96.fsf@alter.siamese.dyndns.org>
In-Reply-To
<512BF61B.4020708@dcon.de>
Karsten Blees <karsten.blees@gmail.com> writes:
Show 11 quoted lines
> Am 25.02.2013 07:43, schrieb Junio C Hamano:
>> Erik Faye-Lund <kusmabite@gmail.com> writes:
> ...
>> I'm in the "marking leftover bits" mode today, and noticed that
>> nothing happened for this topic in my tree. Did msysgit folks expect
>> me to pick this up directly, or did you guys want to feed this series
>> to me (with possibly other changes you worked on outside this list)?
>
> The second patch changes the credential format in a
> backward-incompatible way, so I think this should be in git.git,
> too (better than having two incompatible versions around).

I am a bit confused by that comment, as it was my understanding that the "credential format" only refers to what is stored in the Windows specific credential storage and relevant only to users of msysgit (and I expected folks who are using Git natively on Windows to be using msysgit, not git.git), but in any case, of course we would want a single version and format. My question was if msysgit folks want me to take your patch (which I cannot test myself) and then merge my tree to the msysgit tree as part of their regular updates to catch up with 1.8.2 (and future releases), or they want to test your patches in their tree first, and then either throw me a pull request or send me a patch series with Acked-by:.

I can obviously go either way, but if they expect the former (i.e. I first apply and they pull) while I expect the latter (i.e. they first apply and I pull), then nothing will happen, and if we go the other way around, we would end up getting two copies of the same series. The question was primarily to avoid these possibilities.

-- 
-- 
*** Please reply-to-all at all times ***
*** (do not pretend to know who is subscribed and who is not) ***
*** Please avoid top-posting. ***
The msysGit Wiki is here: https://github.com/msysgit/msysgit/wiki - Github accounts are free.

You received this message because you are subscribed to the Google
Groups "msysGit" group.
To post to this group, send email to msysgit@googlegroups.com
To unsubscribe from this group, send email to
msysgit+unsubscribe@googlegroups.com
For more options, and view previous threads, visit this group at
http://groups.google.com/group/msysgit?hl=en_US?hl=en

--- 
You received this message because you are subscribed to the Google Groups "msysGit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to msysgit+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Previous: Karsten BleesNext: Erik Faye-Lund
Message 9 of 15 in “wincred: improve compatibility with windows versions”
  1. wincred: improve compatibility with windows versionsKarsten Blees, Jan 4, 2013
  2. Erik Faye-LundJan 4, 2013
  3. Karsten BleesJan 8, 2013
  4. Erik Faye-LundJan 8, 2013
  5. 0/2 improve-wincred-compatibilityKarsten Blees, Jan 10, 2013
  6. Erik Faye-LundJan 11, 2013
  7. Junio C HamanoFeb 25, 2013
  8. Karsten BleesFeb 25, 2013
  9. Junio C HamanoFeb 25, 2013
  10. Erik Faye-LundFeb 26, 2013
  11. Junio C HamanoFeb 26, 2013
  12. Johannes SchindelinFeb 26, 2013
  13. 1/2 wincred: accept CRLF on stdin to simplify console usageKarsten Blees, Jan 10, 2013
  14. 2/2 wincred: improve compatibility with windows versionsKarsten Blees, Jan 10, 2013
  15. Erik Faye-LundSep 10, 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.