Re: [GSOC/RFC] GSoC Proposal Draft | Git Beginner

On 21 Mar 2016, at 11:19, Sidhant Sharma wrote: > Hi, > I updated the draft with links, ggit usage examples and some changes to the > timeline. I placed the links with reference here, but in the Google Doc, > they're > inline. > > Thanks and regards, > Sidhant Sharma >

[PATCH v2] branch -D: allow - as abbreviation of '@{-1}'

Signed-off-by: Elena Petrashen --- This micro-patch is meant to allow “-“ as a short-hand for “@{-1} for branch -D (Cf. $gmane/230828): * based on the discussion on the previous version of the patch, added the advice on how to restore the deleted branch using git

[PATCH v2] bisect--helper: convert a function in shell to C

Convert the code literally without changing its design even though it seems that its obscure as to the use of comparing revision to different bisect arguments which seems like a problem in shell because of the way function arguments are handled. The argument handling is kind of hard coded right

git and concurrent access to local repository

Hi, I always thought git allows concurrent access to a repository and expected that this also is true when working with local repositories. The only problem I was aware of is that the use of NFS and windows shares might cause problems. However I sometime see the following error messages in our

Re: [RFC_PATCHv4 4/7] submodule init: redirect stdout to stderr

On Tue, Mar 22, 2016 at 3:06 AM, Stefan Beller wrote: > Reroute the output of stdout to stderr as it is just informative > messages, not to be consumed by machines. Just wondering, what's Git's policy on this? This message is neither an error nor a warning, but just purely

Re: [PATCH 00/16] git bisect improvements

On Mon, Mar 21, 2016 at 11:22 PM, Stephan Beyer wrote: > > Also sorry, I am not following the list so I didn't know there was a > GSoC project for bisect. > >> If it is okay with you then can I work more upon these >> patches in my GSoC project. > > I'm totally fine with that, of

Re: [PATCH] bisect--helper: convert a function in shell to C

On Tue, Mar 22, 2016 at 11:40 AM, Christian Couder wrote: > On Tue, Mar 22, 2016 at 1:28 AM, Stefan Beller wrote: >> On Mon, Mar 21, 2016 at 12:00 PM, Pranit Bauva >> wrote: >>> Convert the code literally without changing

Re: [PATCH] bisect--helper: convert a function in shell to C

On Tue, Mar 22, 2016 at 5:58 AM, Stefan Beller wrote: > On Mon, Mar 21, 2016 at 12:00 PM, Pranit Bauva wrote: >> Convert the code literally without changing its design even though it >> seems that its obscure as to the use of comparing revision to

Re: [PATCH] bisect--helper: convert a function in shell to C

On Tue, Mar 22, 2016 at 1:28 AM, Stefan Beller wrote: > On Mon, Mar 21, 2016 at 12:00 PM, Pranit Bauva wrote: >> Convert the code literally without changing its design even though it >> seems that its obscure as to the use of comparing revision to

<    1   2