Re: [PATCH v2 0/6] Support triangular workflows
- From
Ramkumar Ramachandra <artagnon@gmail.com>
- Date
- Mar 22, 2013, 07:41 UTC
- Message-ID
- <CALkWK0=Mca1YiT0HVVrLrzmN2hGWuMJZPvNKNzb=0H7TxXuYwQ@mail.gmail.com>
- In-Reply-To
- <26A2BE0824FE4C999592D392FCBEF988@PhilipOakley>
Philip Oakley wrote:
Show 33 quoted lines
> From: "Ramkumar Ramachandra" <artagnon@gmail.com> > Sent: Wednesday, March 20, 2013 12:44 PM > >> This follows-up [1], with three important differences: >> >> 1. pushremote_get() and remote_get() share code better. Thanks Jeff. >> >> 2. All spelling mistakes have been corrected. Thanks Eric. >> >> 3. One new test for each of the new configuration variables. The >> extra two parts [2/6] and [3/6] preprare the file for introducing >> tests. However, I've not gone overboard in this preparation; I don't >> replicate the work done by Jonathan in [2]. >> >> Thanks for reading. >> >> [1]: http://thread.gmane.org/gmane.comp.version-control.git/218410 >> [2]: >> http://thread.gmane.org/gmane.comp.version-control.git/218451/focus=218465 >> >> Ramkumar Ramachandra (6): >> remote.c: simplify a bit of code using git_config_string() >> t5516 (fetch-push): update test description >> t5516 (fetch-push): introduce mk_test_with_name() >> remote.c: introduce a way to have different remotes for fetch/push >> remote.c: introduce remote.pushdefault >> remote.c: introduce branch.<name>.pushremote >> >> Documentation/config.txt | 23 +++++++++++++++--- > > > Shouldn't Documentation/gitworkflows.txt also be updated with the triangular > workflow and its configuration?
Currently, Documentation/gitworkflows.txt makes no effort to explain how to set up configuration variables for centralized or distributed workflows. I don't see how I could patch the existing document to include this workflow, without changing the entire structure of the document (left as an exercise for future patches).