From: Alexey Homyakov <alexey.homyakov@gmail.com>
To: git@vger.kernel.org
Subject: The way to make work with git a bit more easier.
Date: Sat, 19 Mar 2011 14:20:12 +0200 [thread overview]
Message-ID: <AANLkTimrYGXQ_wWrj-Sr3UB9YbddW613oebddUoLat7b@mail.gmail.com> (raw)
Hi, guys, i'm enjoy to work with git, but think it's possibly to make
one of the operation more easier.
What do you mean about mark a parts of files which don't need to be
tracked by git once instead using interactive adding each time?
For example using statement in comments like this:
................
tracked part
...............
//@git off
...............
untracked part
...............
//@git on
................
track again
................
It's easy to make git understand all possibly comments definitions.
Thanx.
--
С уважением,
Алексей.
next reply other threads:[~2011-03-19 12:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-19 12:20 Alexey Homyakov [this message]
2011-03-19 12:30 ` The way to make work with git a bit more easier Nguyen Thai Ngoc Duy
2011-03-21 12:33 ` Michael J Gruber
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=AANLkTimrYGXQ_wWrj-Sr3UB9YbddW613oebddUoLat7b@mail.gmail.com \
--to=alexey.homyakov@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.
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).