From: Yagnesh Raghava Yakkala <yagnesh@live.com>
To: nicholas.dokos@hp.com
Cc: emacs-orgmode@gnu.org
Subject: Re: food for thought re. git workflows
Date: Sat, 14 Apr 2012 14:40:02 +0900 [thread overview]
Message-ID: <BLU0-SMTP473786F9CDB443F7CD19193CC380@phx.gbl> (raw)
In-Reply-To: <16725.1334357142@alphaville> (Nick Dokos's message of "Fri, 13 Apr 2012 18:45:42 -0400")
Hello Nicholas,
Nick Dokos <nicholas.dokos@hp.com> writes:
> I thought this was an interesting read:
>
> http://sandofsky.com/blog/git-workflow.html
>
Nice read, I thought cleaning up before merge is good indeed.
Suppose a beginner like me who want to contribute to a bigger projects like org,
wouldn't want put all his stupid, do/undo commits in the org main repository.
So cleaning up(rewriting history) of his own branch with good commit messages
and annotations would help maintainers to review the code. That also gives
more sane look for someone who is coming back to see the commits years later.
Thanks.,
--
YYR
next prev parent reply other threads:[~2012-04-14 5:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-13 22:45 food for thought re. git workflows Nick Dokos
2012-04-14 5:40 ` Yagnesh Raghava Yakkala [this message]
2012-04-14 13:30 ` Carsten Dominik
2012-04-20 12:56 ` Bastien
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BLU0-SMTP473786F9CDB443F7CD19193CC380@phx.gbl \
--to=yagnesh@live.com \
--cc=emacs-orgmode@gnu.org \
--cc=nicholas.dokos@hp.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).