From: Bart Schaefer <schaefer@brasslantern.com>
To: Ray Andrews <rayandrews@eastlink.ca>, Zsh Users <zsh-users@zsh.org>
Subject: Re: git along
Date: Thu, 13 Nov 2014 11:20:48 -0800 [thread overview]
Message-ID: <141113112048.ZM4770@torch.brasslantern.com> (raw)
In-Reply-To: <546501D1.3050608@eastlink.ca>
This is really more suitable for zsh-workers, but to keep the thread in
one place:
On Nov 13, 11:09am, Ray Andrews wrote:
}
} The 'git' manual being longer than War and Peace, let me ask
} some simple questions:
There's a section on "Use of Git" in Etc/zsh-development-guide which has
pointers to additional help.
} git clone git:where-its-coming-from where-its-going-to
}
} ... simple. If I rerun it with the same target dir, will it just
} update, or will it do the full monty all over again?
You don't want to clone again. Use "git pull".
} Would any files I've added be preserved, or nuked?
I don't believe git will ever nuke something that's not under its control,
but I've never done a clone on top of a clone.
} Can we:
}
} git just-show-me-whats-changed ... ?
git status -- to see what files are (not) under git control
git diff -- to see what *you* changed but did not yet commit
git whatchanged -- to see change history of your current source tree
git whatchanged origin/master -- for changes you may not have "pull"ed
next prev parent reply other threads:[~2014-11-13 20:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-13 19:09 Ray Andrews
2014-11-13 18:44 ` Nathan Schwarz
2014-11-13 23:48 ` Ray Andrews
2014-11-13 19:20 ` Bart Schaefer [this message]
2014-11-13 20:01 ` Peter Stephenson
2014-11-14 17:31 ` Bernd Steinhauser
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=141113112048.ZM4770@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=rayandrews@eastlink.ca \
--cc=zsh-users@zsh.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://git.vuxu.org/mirror/zsh/
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).