On 2015-03-05, sebb wrote: > On 5 March 2015 at 05:33, Stefan Bodewig <bode...@apache.org> wrote: >> On 2015-03-05, sebb AT ASF wrote:
>>> <<< >>> git checkout -b release >>> <<< >>> I don't understand what "you're on the release branch" means. >>> Is that what the checkout command does? If so, does it have to be done >>> in an empty directory? >> Unlike svn, git doesn't branch into different folders of the file >> system. You switch branches in place. You issue the "checkout" command >> from inside your working copy and your working tree gets modified to >> reflect the state of the branch. > I don't see how that is different from SVN switch, except that one > does not normally do that. I guess one could view it that way. In git branching is the norm rather than an exception so you change branches quite often. > Does Git switch command remove non-Git files? No, checkout doesn't touch files not controlled by git. > Again, in the case of SVN, a checkout does not necessarily wipe the > directory clean. neither does "git checkout" > If there are any non-versioned (or ignored) files these may be left in place. > This has caused issues on some projects where spurious files have > found their way into release archives. > For this reason it is recommended that SVN checkouts are done into a > new directory. In that case you'd perform a fresh "git clone"[1], change to the new working copy and perform the steps there. Stefan [1] Potentially cloning your "normal" working copy rather than the central server (which allows git to do some tricks with hardlinks on Unix systems) but that's an optimization that probably adds to the confusion rather then helps resolving it. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
