From: Junio C Hamano <gitster@pobox.com>
To: Ron Garret <ron1@flownet.com>
Cc: git@vger.kernel.org
Subject: Re: My use case
Date: Sat, 30 Jan 2010 11:07:29 -0800 [thread overview]
Message-ID: <7vtyu3o1hq.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: ron1-A58BC7.10295430012010@news.gmane.org
Ron Garret <ron1@flownet.com> writes:
> You are absolutely right. That is another reason why having the
> individual files tracked separately from the main project would be a
> good thing if I can get it to work. (It would be kind of like having a
> git-stash on a per-file basis.)
When you have more than one functions defined in a file, and the
interactive Lisp development cycle works primarily on s-exp basis, not
necessarily constrained by file boundaries, don't you want even finer
grained control than "stash per-file"?
I don't think of a good solution myself, but I find your "finer than whole
tree" an interesting topic.
next prev parent reply other threads:[~2010-01-30 19:07 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
2010-01-30 18:29 ` Ron Garret
2010-01-30 19:07 ` Junio C Hamano [this message]
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=7vtyu3o1hq.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--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).