Skip to contentSkip to conversation

help with cvsimport

DISCUSSION Raimund Bauer 2 participants 3 messages Jun 15, 2016

lore
Share & tools
lore
#0 lore raw

Hi,

I unfortunately have to work with several cvs-repositories and was wondering if there was a way to have the files processed on import:
- strip trailing whitespace
- convert to newline-only line endings

Knowing git there probably is already a way to do that - I'd appreciate any rtfm-pointers ...

Many thanks in advance

Signature · 3 lines
best regards

  Ray
#1 lore raw

Hi,

Quoted 4 lines · Raimund Bauer

I unfortunately have to work with several cvs-repositories and was wondering if there was a way to have the files processed on import:
- strip trailing whitespace
- convert to newline-only line endings

If you want to use cvsimport incrementally, I'd rather not process the "origin" branch like this, but rather use git-filter-branch (with a simple index filter) to do that.

Even if you do not want to use it incrementally, it seems easier and cleaner (if somewhat slower) to me.

So, something like

	git filter-branch --index-filter 'git ls-files |
		while read name; do
			perl -pi -e "s/[ \009\015]*$//" "$name"
		done
		git add -u' cleaned-up-origin

should do.

Hth,
Dscho

#2 lore raw

Hi,

* Johannes Schindelin wrote, On 23.06.2007 13:27:

Quoted 17 lines

Hi,

Quoted 5 lines · Raimund Bauer

I unfortunately have to work with several cvs-repositories and was wondering if there was a way to have the files processed on import:
- strip trailing whitespace
- convert to newline-only line endings

If you want to use cvsimport incrementally, I'd rather not process the "origin" branch like this, but rather use git-filter-branch (with a simple index filter) to do that.

Even if you do not want to use it incrementally, it seems easier and cleaner (if somewhat slower) to me.

So, something like

Quoted 8 lines
	git filter-branch --index-filter 'git ls-files |
		while read name; do
			perl -pi -e "s/[ \009\015]*$//" "$name"
		done
		git add -u' cleaned-up-origin

should do.

Thanks, will try that out.
Tough I'm not very happy about having to create an extra branch for every branch I want to work with. And a git-solution would also respect git-attributes ...

Quoted 3 lines

Hth,
Dscho

Signature · 3 lines
best regards

 Ray