From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.8.1-0.1
Date: Tue, 27 Jun 2017 19:05:00 -0000 [thread overview]
Message-ID: <87lgods12r.fsf@Rainer.invalid> (raw)
In-Reply-To: <58606f41-68f7-a157-3108-e6ce46443eb1@SystematicSw.ab.ca> (Brian Inglis's message of "Tue, 27 Jun 2017 12:53:30 -0600")
Brian Inglis writes:
> Nearly always forget the branch part: gotta retrain my fingers
> to add the appropriate branch commands for the source control
> products I use, and do more granular commits instead of big bangs.
The thing to remember is that with git you can just as easily create the
branch when you are about to commit your first change or even
retroactively.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Wavetables for the Terratec KOMPLEXER:
http://Synth.Stromeko.net/Downloads.html#KomplexerWaves
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2017-06-27 19:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-22 14:31 Corinna Vinschen
2017-06-23 17:53 ` Marco Atzeri
2017-06-23 18:25 ` Corinna Vinschen
2017-06-23 18:47 ` Brian Inglis
2017-06-26 8:31 ` Corinna Vinschen
2017-06-26 16:25 ` Brian Inglis
2017-06-26 16:42 ` Corinna Vinschen
2017-06-26 20:00 ` Brian Inglis
2017-06-27 1:20 ` Andrey Repin
2017-06-27 5:33 ` Brian Inglis
2017-06-27 7:56 ` Corinna Vinschen
2017-06-27 18:53 ` Brian Inglis
2017-06-27 19:05 ` Achim Gratz [this message]
2017-06-27 20:37 ` Brian Inglis
2017-06-27 7:38 ` Corinna Vinschen
2017-06-24 7:35 ` Marco Atzeri
2017-06-26 8:32 ` Corinna Vinschen
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=87lgods12r.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=cygwin@cygwin.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 read-only IMAP folder(s) and NNTP newsgroup(s).