You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Troy Curtis Jr <tr...@gmail.com> on 2006/09/18 05:17:05 UTC
svn commit usage survey
I am in the process of writing a wrapper script for 'svn commit' that
will allow me to delete paths from the log message that I do not want
to commit. I got the idea of this functionality from SVK and
immediately saw the usefulness. Several ":q!", <answer "a" to abort
questions> later I decided that I HAD to have that functionality.
My questions to the list are:
How do you typically use 'svn commit' when you have some files you do
not want in the commit?
Do you often run into an issue where you have one file that you do not
want to commit, directly beside several that you do?
Is the only option in this case manually specifying every file you
*do* want to include in the commit? Or am I missing something?
It seems to me that this would be a common occurrence and so it really
surprises me that a similar wrapper script has not already been
written. But perhaps I am using Subversion in an atypical manner?
What are your thoughts?
Troy
--
"Beware of spyware. If you can, use the Firefox browser." - USA Today
Download now at http://getfirefox.com
Registered Linux User #354814 ( http://counter.li.org/)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: svn commit usage survey
Posted by Grant Rettke <gr...@acm.org>.
Hi Troy,
I'm not sure that I completely understand your situation, so here is my
attempt at an answer.
If you are working from the command line, within a working copy, and you
start creating files within that directory, and then you type 'svn status'
you will see that all of the files have a '?' next to them. If you type
'svn commit' nothing will happen.
If you type 'svn add *' then they will be under version control and when
you type 'svn commit' they will get committed.
If you only want to commit a single type 'svn commit <filename>'.
If you want to ignore file so they don't show up in status you need to
edit the svn:ignore property on your directory.
Does sort of answer your question or am I too far off?
Quoting Troy Curtis Jr <tr...@gmail.com>:
> I am in the process of writing a wrapper script for 'svn commit' that
> will allow me to delete paths from the log message that I do not want
> to commit. I got the idea of this functionality from SVK and
> immediately saw the usefulness. Several ":q!", <answer "a" to abort
> questions> later I decided that I HAD to have that functionality.
>
> My questions to the list are:
>
> How do you typically use 'svn commit' when you have some files you do
> not want in the commit?
> Do you often run into an issue where you have one file that you do not
> want to commit, directly beside several that you do?
> Is the only option in this case manually specifying every file you
> *do* want to include in the commit? Or am I missing something?
>
> It seems to me that this would be a common occurrence and so it really
> surprises me that a similar wrapper script has not already been
> written. But perhaps I am using Subversion in an atypical manner?
>
> What are your thoughts?
> Troy
>
> --
> "Beware of spyware. If you can, use the Firefox browser." - USA Today
> Download now at http://getfirefox.com
> Registered Linux User #354814 ( http://counter.li.org/)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: svn commit usage survey
Posted by Peter Werner <l....@vasas.no-ip.org>.
> How do you typically use 'svn commit' when you have some files you do
> not want in the commit?
Just specify the files by copy-paste from svn st output.
> Do you often run into an issue where you have one file that you do not
> want to commit, directly beside several that you do?
Yes. Actually what happens that I want to break my changes into
different commits (small but complete changes).
> Is the only option in this case manually specifying every file you
> *do* want to include in the commit? Or am I missing something?
Not the only way but the easiest. I don't think you miss something.
> What are your thoughts?
It's really good feature in svk, I'm inetrested about your results.
WP
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: svn commit usage survey
Posted by Erik Forsberg <fo...@cendio.se>.
Duncan Murdoch <mu...@stats.uwo.ca> writes:
> Can you describe what your script does? The things I like about tsvn
> for a big commit are:
>
> - the ability to review and edit the list of files to commit after
> asking for the commit, but before committing
>
> - the ability to get information on what changes are in each file
> before making the include/exclude decision. This lets me recognize
> when files contain only whitespace changes, etc.
I use 'M-x svn-status' in emacs, part of the psvn elisp package. It
lets me do just that, and it'll probably work as well in Emacs on
Windows as it does for me in Emacs on Linux.
Cheers,
\EF
--
Erik Forsberg OpenSource-based Thin Client Technology
Systems Analyst/Developer Phone: +46-13-21 46 00
Cendio AB Web: http://www.cendio.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: svn commit usage survey
Posted by Duncan Murdoch <mu...@stats.uwo.ca>.
On 9/19/2006 8:23 AM, Peter Werner wrote:
>> - the ability to review and edit the list of files to commit after
>> asking for the commit, but before committing
>
> That's the purpose of Duncan's wrapper (if I understood correctly). It
> is no use for tsvn users just for commandline guys.
I suspect there are a lot of mixed users like me. I use svn on MacOSX,
FreeBSD and Linux as well as on Windows, and I'm interested in the
wrapper. (BTW, it's Troy's wrapper, not mine.)
Duncan Murdoch
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: svn commit usage survey
Posted by Peter Werner <l....@vasas.no-ip.org>.
> - the ability to review and edit the list of files to commit after
> asking for the commit, but before committing
That's the purpose of Duncan's wrapper (if I understood correctly). It
is no use for tsvn users just for commandline guys.
WP
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: svn commit usage survey
Posted by Duncan Murdoch <mu...@stats.uwo.ca>.
On 9/19/2006 12:09 AM, Troy Curtis Jr wrote:
> On 9/18/06, Duncan Murdoch <mu...@stats.uwo.ca> wrote:
>> On 9/18/2006 1:17 AM, Troy Curtis Jr wrote:
>>> I am in the process of writing a wrapper script for 'svn commit' that
>>> will allow me to delete paths from the log message that I do not want
>>> to commit. I got the idea of this functionality from SVK and
>>> immediately saw the usefulness. Several ":q!", <answer "a" to abort
>>> questions> later I decided that I HAD to have that functionality.
>>>
>>> My questions to the list are:
>>>
>>> How do you typically use 'svn commit' when you have some files you do
>>> not want in the commit?
>> In a case like that I'd almost certainly use TortoiseSVN. It lists all
>> the files that it will commit, and allows you to uncheck those which you
>> don't want to commit. (There are various convenient ways to select what
>> goes in that list in the first place, too.)
>>
>> It sounds as though you're not using Windows, but I'd suggest taking a
>> look at a Windows machine running tsvn before writing your own script:
>> they've done a really good job on the user interface.
>>
>> And if you *are* using Windows, then use TortoiseSVN, don't waste time
>> writing a script to do what it does.
>>
>> Duncan Murdoch
>>
>>> Do you often run into an issue where you have one file that you do not
>>> want to commit, directly beside several that you do?
>>> Is the only option in this case manually specifying every file you
>>> *do* want to include in the commit? Or am I missing something?
>>>
>>> It seems to me that this would be a common occurrence and so it really
>>> surprises me that a similar wrapper script has not already been
>>> written. But perhaps I am using Subversion in an atypical manner?
>>>
>>> What are your thoughts?
>>> Troy
>>>
>>
>
> I am not currently using Windows (thank goodness! :-) ), but I do like
> the TortoiseSVN client, at least for browsing and occasional commits.
> However, I certainly wouldn't want to fire up a GUI for every commit
> (I'm a command line kinda guy).
>
> Grant: The situation that I am refering to is one where you actually
> work on two seperate tasks in the same working copy and then need to
> commit one as a set, but not the other AND the files are interspersed
> throughout the code.
>
> So I actually just finished a rough, working version of my script. I
> need to go through and clean it up before I release it for all the
> world to see (hopefully sometime tommorrow). It was a great feeling
> to delete a file out of a commit within vim! It is written in perl
> and currently uses system calls to interact with svn. I would really
> have liked to use the perl bindings, but they do not currently support
> locking relative to the repository :-(, and it is a feature that I
> need.
Can you describe what your script does? The things I like about tsvn
for a big commit are:
- the ability to review and edit the list of files to commit after
asking for the commit, but before committing
- the ability to get information on what changes are in each file
before making the include/exclude decision. This lets me recognize when
files contain only whitespace changes, etc.
I'm a GUI sort of guy so I find tsvn's way of offering these options
very nice, but I can imagine there are other ways.
Duncan Murdoch
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: svn commit usage survey
Posted by Troy Curtis Jr <tr...@gmail.com>.
On 9/18/06, Duncan Murdoch <mu...@stats.uwo.ca> wrote:
> On 9/18/2006 1:17 AM, Troy Curtis Jr wrote:
> > I am in the process of writing a wrapper script for 'svn commit' that
> > will allow me to delete paths from the log message that I do not want
> > to commit. I got the idea of this functionality from SVK and
> > immediately saw the usefulness. Several ":q!", <answer "a" to abort
> > questions> later I decided that I HAD to have that functionality.
> >
> > My questions to the list are:
> >
> > How do you typically use 'svn commit' when you have some files you do
> > not want in the commit?
>
> In a case like that I'd almost certainly use TortoiseSVN. It lists all
> the files that it will commit, and allows you to uncheck those which you
> don't want to commit. (There are various convenient ways to select what
> goes in that list in the first place, too.)
>
> It sounds as though you're not using Windows, but I'd suggest taking a
> look at a Windows machine running tsvn before writing your own script:
> they've done a really good job on the user interface.
>
> And if you *are* using Windows, then use TortoiseSVN, don't waste time
> writing a script to do what it does.
>
> Duncan Murdoch
>
> > Do you often run into an issue where you have one file that you do not
> > want to commit, directly beside several that you do?
> > Is the only option in this case manually specifying every file you
> > *do* want to include in the commit? Or am I missing something?
> >
> > It seems to me that this would be a common occurrence and so it really
> > surprises me that a similar wrapper script has not already been
> > written. But perhaps I am using Subversion in an atypical manner?
> >
> > What are your thoughts?
> > Troy
> >
>
>
I am not currently using Windows (thank goodness! :-) ), but I do like
the TortoiseSVN client, at least for browsing and occasional commits.
However, I certainly wouldn't want to fire up a GUI for every commit
(I'm a command line kinda guy).
Grant: The situation that I am refering to is one where you actually
work on two seperate tasks in the same working copy and then need to
commit one as a set, but not the other AND the files are interspersed
throughout the code.
So I actually just finished a rough, working version of my script. I
need to go through and clean it up before I release it for all the
world to see (hopefully sometime tommorrow). It was a great feeling
to delete a file out of a commit within vim! It is written in perl
and currently uses system calls to interact with svn. I would really
have liked to use the perl bindings, but they do not currently support
locking relative to the repository :-(, and it is a feature that I
need.
Troy
--
"Beware of spyware. If you can, use the Firefox browser." - USA Today
Download now at http://getfirefox.com
Registered Linux User #354814 ( http://counter.li.org/)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: svn commit usage survey
Posted by Duncan Murdoch <mu...@stats.uwo.ca>.
On 9/18/2006 1:17 AM, Troy Curtis Jr wrote:
> I am in the process of writing a wrapper script for 'svn commit' that
> will allow me to delete paths from the log message that I do not want
> to commit. I got the idea of this functionality from SVK and
> immediately saw the usefulness. Several ":q!", <answer "a" to abort
> questions> later I decided that I HAD to have that functionality.
>
> My questions to the list are:
>
> How do you typically use 'svn commit' when you have some files you do
> not want in the commit?
In a case like that I'd almost certainly use TortoiseSVN. It lists all
the files that it will commit, and allows you to uncheck those which you
don't want to commit. (There are various convenient ways to select what
goes in that list in the first place, too.)
It sounds as though you're not using Windows, but I'd suggest taking a
look at a Windows machine running tsvn before writing your own script:
they've done a really good job on the user interface.
And if you *are* using Windows, then use TortoiseSVN, don't waste time
writing a script to do what it does.
Duncan Murdoch
> Do you often run into an issue where you have one file that you do not
> want to commit, directly beside several that you do?
> Is the only option in this case manually specifying every file you
> *do* want to include in the commit? Or am I missing something?
>
> It seems to me that this would be a common occurrence and so it really
> surprises me that a similar wrapper script has not already been
> written. But perhaps I am using Subversion in an atypical manner?
>
> What are your thoughts?
> Troy
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org