From: tytso@mit.edu
To: Ron Garret <ron1@flownet.com>
Cc: git@vger.kernel.org
Subject: Re: My use case
Date: Sat, 30 Jan 2010 12:48:44 -0500 [thread overview]
Message-ID: <20100130174844.GD788@thunk.org> (raw)
In-Reply-To: <ron1-CC0A6E.00541330012010@news.gmane.org>
On Sat, Jan 30, 2010 at 12:54:13AM -0800, Ron Garret wrote:
> Don't forget, I'm integrating this *into* the IDE, not just using it
> *for* the IDE. So I want to just have a context menu on each code
> window with "SNAPSHOT" and "ROLLBACK" items that Just Work. The casual
> user won't even know that there's git behind the scenes.
This is a workflow question, I suppose, but I find things work much
better if you can get the user to give you explicit commit boundaries
so that (a) bisect works, and (b) they can describe what each commit
does, and (c) so they can more easily move specific bug fixes or
features between different release branches. The free-form hacking
more may be nice, and very "LISP-like", but there are some real
advantages to having explicitly describable and documented commits.
Best regards,
- Ted
next prev parent reply other threads:[~2010-01-30 17:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-30 8:26 My use case Ron Garret
2010-01-30 8:47 ` Edward Z. Yang
2010-01-30 8:54 ` Ron Garret
2010-01-30 17:48 ` tytso [this message]
2010-01-30 18:29 ` Ron Garret
2010-01-30 19:07 ` Junio C Hamano
2010-01-30 19:19 ` Ron Garret
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100130174844.GD788@thunk.org \
--to=tytso@mit.edu \
--cc=git@vger.kernel.org \
--cc=ron1@flownet.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.
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 NNTP newsgroup(s).