From: "Patrick Doyle" <wpdster@gmail.com>
To: git <git@vger.kernel.org>
Subject: workflow question
Date: Tue, 24 Jul 2007 09:53:30 -0400 [thread overview]
Message-ID: <e2a1d0aa0707240653x55dd82b3pf9e3986f5c3bb344@mail.gmail.com> (raw)
I'm still trying to figure out how to adapt my workflow to git or git
to my workflow, and I've come up with yet another question or two...
I tend to work detached from our central SVN server, and I'm attracted
to the fact that I can work on my laptop, commit changes as I go
along, and later synchronize them back to the server.
On my current project, I am sole developer (at present) and the
central SVN server serves primarly as an off-site backup and
historical archive.
Enough of the setup, here are the questions...
1) I would like to make a (git) branch on which I can commit
hourly/daily/periodically as I add in a new feature (so that I can
roll back to the "Gee, I thought it was behaving yesterday -- what
does that code look like?" commit when I need to), but I don't want to
send all of the "commit as of 12:32 on Thursday" commits back to the
SVN server when I'm done. Do I want to use a "squash" merge to merge
my changes back to the master branch before I synchronize with the
subversion server? Or do I use the "--no-commit" option to merge? Or
do I try something else? The first/last time I tried this, I ended up
with a fast-forward merge back into master, which included all of my
stupid little commit messages. I would rather one commit message that
read "Added XYZ feature".
2) When I don't fork a branch, and I don't commit until I've completed
the particular feature I'm working on, I can get a fairly good idea of
where I am and what I was doing last (which might be 5-7 days ago,
given high priority interrupts on other projects, summer vacations,
etc...) just by running a "git status". I see that there are 7 new
files, and 2 modified files. I know that, when I fork my branch, I
can use "git diff master" to see what's different between my branch
and the master, but then I get the diff of all of the changes as well,
which is too much information. "git diff --name-only" and "git diff
--summary" are closer, but I can't tell what's been added vs. what's
been changed. Any suggestions?
As an aside, is there an undocumented option to "git status" to
produce a less verbose report of what's been changed and what's not
checked in? Perhaps a single line per file with a one or two letter
indication of the status of the file followed by the name? If not,
would there be any violent objections to my submitting a patch to add
such a feature?
That's enough for now. Thanks for reading this far :-)
--wpd
next reply other threads:[~2007-07-24 13:53 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-24 13:53 Patrick Doyle [this message]
2007-07-24 15:37 ` workflow question Alex Riesen
2007-07-24 16:30 ` Patrick Doyle
2007-07-24 16:35 ` Julian Phillips
2007-07-24 20:54 ` Alex Riesen
2007-07-24 20:57 ` Alex Riesen
2007-07-24 21:00 ` J. Bruce Fields
2007-07-24 21:38 ` Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2007-09-25 16:43 Workflow question Russ Brown
2007-09-25 19:09 ` Andreas Ericsson
2007-09-25 19:34 ` Jeff King
2007-09-25 19:50 ` Wincent Colaiuta
2007-09-25 20:20 ` Jeff King
2007-09-25 20:37 ` Wincent Colaiuta
2007-09-25 19:42 ` Russ Brown
2007-09-25 20:17 ` Jeff King
2007-09-25 20:56 ` Russ Brown
2007-09-25 21:28 ` Junio C Hamano
2007-09-26 0:01 ` Russ Brown
2007-09-26 0:47 ` Jeff King
2007-09-26 1:51 ` Karl Hasselström
2007-09-26 2:55 ` Russ Brown
2007-09-26 5:29 ` Junio C Hamano
2007-09-26 12:42 ` Jeff King
2007-09-25 22:38 ` Andreas Ericsson
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: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e2a1d0aa0707240653x55dd82b3pf9e3986f5c3bb344@mail.gmail.com \
--to=wpdster@gmail.com \
--cc=git@vger.kernel.org \
/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://80x24.org/mirrors/git.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).