[svnbook commit] r2901 - trunk/src/en/book
Brian W. Fitzpatrick
fitz at red-bean.com
Sat Dec 8 17:00:37 CST 2007
Great.
Fucking computers...
-Fitz
On Dec 8, 2007 4:55 PM, Ben Collins-Sussman <sussman at red-bean.com> wrote:
> Nonsense... red-bean is messing up. I sent my two suggestions at 3:13
> and 3:25pm, only 12 minutes apart. You replied to the first one at
> 4:16pm, so there must have been a massive delay before you saw my
> second mail...
>
>
>
> On Dec 8, 2007 4:39 PM, Brian W. Fitzpatrick <fitz at red-bean.com> wrote:
> > Thanks. Especially for sending that after I committed the last change.
> >
> > -Fitz
> >
> > PS :)
> >
> >
> > On Dec 8, 2007 3:25 PM, Ben Collins-Sussman <sussman at red-bean.com> wrote:
> > > Oh yeah, one other thing: a lot of newbies ask, "why the heck doesn't
> > > a commit just bump everything in the working copy?" The answer is
> > > explained in detail at
> > > http://svnbook.red-bean.com/nightly/en/svn-book.html#svn.basic.in-action.mixedrevs.update-commit.
> > > I think it would be great to have an <xref> in your sidebar pointing
> > > to that.
> > >
> > > On Dec 8, 2007 3:13 PM, Ben Collins-Sussman <sussman at red-bean.com> wrote:
> > >
> > > > Some feedback: I think it's misleading to say that the parent
> > > > directory is "out of date".... that phrase connotes that there's newer
> > > > data waiting for it on the server. A simpler explanation is to say:
> > > > hey, 'svn commit' only bumps the revision of the things it commits,
> > > > and so usually the parent directory remains at the "older" revision.
> > > > 'svn log' then defaults to grabbing the history of the directory at
> > > > its current revision, and thus you don't see the newly-committed
> > > > changes.
> > > >
> > > >
> > > >
> > > >
> > > > On Dec 8, 2007 1:48 PM, fitz <noreply at red-bean.com> wrote:
> > > > > Author: fitz
> > > > > Date: Sat Dec 8 13:48:24 2007
> > > > > New Revision: 2901
> > > > >
> > > > > Log:
> > > > > Explain why 'svn commit ; svn log' doesn't show your last log message.
> > > > >
> > > > > This fixes issue #38.
> > > > >
> > > > > * src/en/book/ch02-basic-usage.xml: I'd rather be sleeping!
> > > > >
> > > > >
> > > > > Modified:
> > > > > trunk/src/en/book/ch02-basic-usage.xml
> > > > >
> > > > > Modified: trunk/src/en/book/ch02-basic-usage.xml
> > > > > ==============================================================================
> > > > > --- trunk/src/en/book/ch02-basic-usage.xml (original)
> > > > > +++ trunk/src/en/book/ch02-basic-usage.xml Sat Dec 8 13:48:24 2007
> > > > > @@ -1556,6 +1556,31 @@
> > > > > for those revisions in which the working file (or URL)
> > > > > changed.</para>
> > > > >
> > > > > + <sidebar>
> > > > > +
> > > > > + <title>Why Does <command>svn log</command> Not Show Me What I
> > > > > + Just Committed?</title>
> > > > > +
> > > > > + <para>If you make a commit and immediately type <command>svn
> > > > > + log</command> with no arguments, you may notice that your
> > > > > + most recent commit doesn't show up in the list of log
> > > > > + messages. This is due to a combination of the behavior of
> > > > > + <command>svn commit</command> and the default behavior of
> > > > > + <command>svn log</command>. First, when you commit changes
> > > > > + to the repository, only the files (and directories) that you
> > > > > + changed are <quote>updated</quote> to the latest revision,
> > > > > + so unless you updated a property on your current directory,
> > > > > + your commit leaves that directory <quote>out of
> > > > > + date</quote>. When you run <command>svn log</command> with
> > > > > + no arguments, it takes the latest revision from your current
> > > > > + working directory, which is out of date, so you don't see
> > > > > + your latest commit. The solution here is to either update
> > > > > + your working copy or explicitly provide a revision number to
> > > > > + <command>svn log</command> by using the <option>--revision</option>
> > > > > + (<option>-r</option>) option.</para>
> > > > > +
> > > > > + </sidebar>
> > > > > +
> > > > > <para>If you want even more information about a file or
> > > > > directory, <command>svn log</command> also takes a
> > > > > <option>--verbose (-v)</option> option. Because Subversion
> > > > >
> > > > > _______________________________________________
> > > > > svnbook-dev mailing list
> > > > > svnbook-dev at red-bean.com
> > > > > http://www.red-bean.com/mailman/listinfo/svnbook-dev
> > > > >
> > > >
> > >
> > > _______________________________________________
> > > svnbook-dev mailing list
> > > svnbook-dev at red-bean.com
> > > http://www.red-bean.com/mailman/listinfo/svnbook-dev
> > >
> > >
> >
>
>
More information about the svnbook-dev
mailing list