Date: Thu, 25 Jun 2020 08:24:55 +0200 From: Emanuel Haupt <ehaupt@FreeBSD.org> To: Ed Maste <emaste@freebsd.org> Cc: freebsd-git@freebsd.org Subject: Re: svn primer translation to git Message-ID: <20200625082455.9f1343f6f353f4be24385bc6@FreeBSD.org> In-Reply-To: <CAPyFy2Dy4cLQpgUsk_ushXsQFvRPk2S8SEfgWF=0xibGRGJvKw@mail.gmail.com> References: <CAPyFy2Dy4cLQpgUsk_ushXsQFvRPk2S8SEfgWF=0xibGRGJvKw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Ed Maste <emaste@freebsd.org> wrote: > We currently have a FreeBSD Subversion primer in the committer's > guide: > https://www.freebsd.org/doc/en_US.ISO8859-1/articles/committers-guide/subversion-primer.html > > I've started a translation of this into a Git primer, at: > https://hackmd.io/ML5TSl8mQ5-27B5eqDf7YA?view > > I'm particularly interested in feedback on how much git background / > theory of operation we want to include here (vs referring to external > documentation). Thank you for writing the document. Maybe we could address the convention [1] that with git commit messages usually begin with a subject, followed by a blank line and then the commit body. This schema produces beautiful commit logs on web-based DevOps lifecycle tools such as github, gitlab, gitea. I further recommend this [2] article on the subject. Emanuel [1] https://git-scm.com/docs/git-commit#_discussion [2] https://chris.beams.io/posts/git-commit/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20200625082455.9f1343f6f353f4be24385bc6>