Re: What's cooking in git.git (Mar 2014, #03; Fri, 14)
- From
Ramkumar Ramachandra <artagnon@gmail.com>
- Date
- Mar 16, 2014, 23:15 UTC
- Message-ID
- <CALkWK0npxgi2gWQbuYZLn_N0GxgTdPTR8c-yhgCxEV=mM2Zngw@mail.gmail.com>
- In-Reply-To
- <EA1EF5746EA7414CAE1320AA61100178@PhilipOakley>
Philip Oakley wrote:
Show 12 quoted lines
>> * po/everyday-doc (2014-01-27) 1 commit >> - Make 'git help everyday' work >> >> This may make the said command to emit something, but the source is >> not meant to be formatted into a manual pages to begin with, and >> also its contents are a bit stale. It may be a good first step in >> the right direction, but needs more work to at least get the >> mark-up right before public consumption. > > I'm not sure what elements you feel need adjustment. At the moment the > markup formats quite reasonably to my eyes, both as an HTML page and as a > man page.
I sent you a small patch fixing some minor markup issues.
Show 7 quoted lines
> That said, the (lack of) introduction could do with a paragraph to introduce
> the "guide". I have something in draft..
>
> I had a thought that it may be worth a slight rearrangement to add a section
> covering the setting up of one's remotes, depending whether it was forked,
> corporate, or independent, but the lack of resolution on the next
> {publish/push} topic makes such a re-write awkward at this stage. (Ram cc'd)Before attempting to introduce remote.pushdefault and triangular workflows, I'd first fix the main issue: stale content. I'm not sure who uses git show-branch or mailx anymore, for instance.