From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Steffen Prohaska <prohaska@zib.de>
Cc: Theodore Tso <tytso@mit.edu>, Johan Herland <johan@herland.net>,
git@vger.kernel.org, "Shawn O. Pearce" <spearce@spearce.org>,
Miles Bader <miles@gnu.org>
Subject: Re: way to automatically add untracked files?
Date: Mon, 6 Aug 2007 01:17:52 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0708060116590.14781@racer.site> (raw)
In-Reply-To: <C3725674-7B33-4B2F-9386-704540D51C0E@zib.de>
Hi,
On Sun, 5 Aug 2007, Steffen Prohaska wrote:
>
> On Aug 5, 2007, at 6:11 PM, Theodore Tso wrote:
>
> > On Sun, Aug 05, 2007 at 02:11:24PM +0200, Johan Herland wrote:
> > > $ hg addremove --help
> > > hg addremove [OPTION]... [FILE]...
> > >
> > > add all new files, delete all missing files
> > >
> > > Add all new files and remove all missing files from the repository.
> > >
> > > New files are ignored if they match any of the patterns in .hgignore.
> > > As
> > > with add, these changes take effect at the next commit.
> > >
> > > Adding a git-addremove command should not be much work, and it would be a
> > > lot friendlier to people whose workflow is more aligned with #2 than #1.
> >
> > Not much work at all:
> >
> > # git config --system --add alias.addremove "git add . ; git add -u"
>
> But how can I handle the [FILE]... from above?
See
http://git.or.cz/gitwiki/Aliases#head-714f0aa64cb53eda636d41e16bf2b99477588685
Hth,
Dscho
next prev parent reply other threads:[~2007-08-06 0:18 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-05 3:31 way to automatically add untracked files? Miles Bader
2007-08-05 3:58 ` Shawn O. Pearce
2007-08-05 4:13 ` Junio C Hamano
2007-08-05 4:00 ` Miles Bader
2007-08-05 4:13 ` Shawn O. Pearce
2007-08-05 4:22 ` Miles Bader
2007-08-05 4:23 ` Junio C Hamano
2007-08-05 4:30 ` Miles Bader
2007-08-05 4:39 ` Junio C Hamano
2007-08-05 4:53 ` Miles Bader
2007-08-05 5:04 ` Junio C Hamano
2007-08-05 5:17 ` Miles Bader
2007-08-05 5:23 ` Johannes Schindelin
2007-08-05 5:27 ` Miles Bader
2007-08-05 11:22 ` Steffen Prohaska
2007-08-05 12:11 ` Johan Herland
2007-08-05 12:17 ` David Kastrup
2007-08-05 16:11 ` Theodore Tso
2007-08-05 19:16 ` Johan Herland
2007-08-06 0:00 ` Miles Bader
2007-08-06 0:16 ` Johannes Schindelin
2007-08-06 3:09 ` Miles Bader
2007-08-06 3:21 ` Johannes Schindelin
2007-08-06 3:45 ` Miles Bader
2007-08-06 7:46 ` Johan Herland
2007-08-06 12:17 ` Johannes Schindelin
2007-08-05 20:04 ` Steffen Prohaska
2007-08-06 0:17 ` Johannes Schindelin [this message]
2007-08-06 4:58 ` Steffen Prohaska
2007-08-06 0:32 ` Jakub Narebski
2007-08-06 7:30 ` Johan Herland
2007-08-06 8:45 ` Junio C Hamano
2007-08-06 18:19 ` David Kastrup
2007-08-07 0:08 ` Miles Bader
2007-08-05 5:03 ` Linus Torvalds
2007-08-05 5:14 ` Junio C Hamano
2007-08-05 7:32 ` David Kastrup
2007-08-05 10:33 ` Benchmarking git-add vs git-ls-files+update-index (was: way to automatically add untracked files?) David Kastrup
2007-08-05 7:34 ` way to automatically add untracked files? Miles Bader
2007-08-05 17:04 ` Linus Torvalds
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=Pine.LNX.4.64.0708060116590.14781@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=johan@herland.net \
--cc=miles@gnu.org \
--cc=prohaska@zib.de \
--cc=spearce@spearce.org \
--cc=tytso@mit.edu \
/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).