[PATCH] allow commentChars in commit messages

From: Corentin Bompard Add new argument which permits stripspace to escape backslashes in order to have commit messages which begins with commentChars and backslashes. Add new function strbuf_addbackslash which adds a backslash before commentChars and other backslashes used by git commit

[PATCH] [WIP/RFC] add git pull and git fetch --set-upstream

-main-repo git pull --set-upstream main master or, instead of the last line git fetch --set-upstream main master git merge # or git rebase This fonctionality works like git push --set-upstream. Signed-off-by: Corentin BOMPARD Signed-off-by: Nathan BERBEZIER Signed-off-by: Pablo

Re: [PATCH] [WIP/RFC] add git pull and git fetch --set-upstream

>Corentin BOMPARD writes: > >> Add the --set-upstream option to git pull/fetch >> which lets the user set the upstream configuration >> for the current branch. > > I think it is a good idea to mention what you exactly mean by "the > upstream configuratio

[PATCH] [WIP/RFC] add git pull and git fetch --set-upstream

--set-upstream or, instead of the last line git fetch main master --set-upstream git merge # or git rebase This foncionality works like git push --set-upstream. Signed-off-by: Corentin BOMPARD Signed-off-by: Nathan BERBEZIER Signed-off-by: Pablo CHABANNE Signed-off-by: Matthieu MOY

Re: [PATCH] [WIP/RFC] add git pull and git fetch --set-upstream

> BOMPARD CORENTIN p1603631 writes: > >> Adding the --set-upstream option to git pull/fetch > > We usually write commit messages with imperative tone, hence "add", not > "adding". Fixed. >> +/* >> + * We want to set the current branch config following the >> +

[PATCH] [WIP/RFC] add git pull and git fetch --set-upstream

--set-upstream or, instead of the last line git fetch main master --set-upstream git merge # or git rebase This foncionality works like git push --set-upstream. Signed-off-by: Corentin BOMPARD Signed-off-by: Nathan BERBEZIER Signed-off-by: Pablo CHABANNE Signed-off-by: Matthieu MOY

[PATCH 2/2 v3] doc: format pathnames and URLs as monospace.

Applying CodingGuidelines about monospace on pathnames and URLs. See Documentation/CodingGuidelines.txt for more information. Signed-off-by: Corentin BOMPARD Signed-off-by: Nathan BERBEZIER Signed-off-by: Pablo CHABANNE Signed-off-by: Matthieu MOY --- Changes: We listen to Matthieu MOY and

[PATCH 1/2 v3] doc/CodingGuidelines: URLs and paths as monospace.

higher in the second case. At least, this shows that the existing documentation uses inconsistent formatting, and that it would be good to do something about it. * It may be debatable whether path names need to be typed in monospace but having them in italics is really unusual. Signed-of

[PATCH v2] doc: format pathnames and URLs as monospace

Updating the documentation to use monospace on URLs and pathnames because it makes more sense Signed-off-by: Corentin BOMPARD Signed-off-by: Nathan BERBEZIER Signed-off-by: Pablo CHABANNE --- Changes: Dropped modifications on refs Documentation/SubmittingPatches| 6

[PATCH] doc: format pathnames and URLs as monospace

Signed-off-by: Corentin BOMPARD --- Documentation/SubmittingPatches| 6 ++-- Documentation/config/checkout.txt | 2 +- Documentation/config/core.txt | 14 Documentation/config/log.txt | 4