[git-users] Re: Use Git to manage .NET assembly version

2010-08-31 Thread P Rouleau
At my place, we use an AssemblyInfo-Custom.template which contains the
common attributs, like the company' name and copyrights. That file is
keep in a template/ directory and it is shared with all the projects
of a solution. The standard AssemblyInfo.cs is cleaned to only
contains the attributs specific to the project, like its name. The
file also contains the version's attributs, but they have MACRO
instead of version X.Y.Z.W.

The macros are replaced with the help of an script called from the pre-
build event. The script copies the template from the template/
directory to the properties's project directory and replace the macros
with a version generated with the help of "git describe". You can
search for GIT-VERSION-GEN for an example how to use "git describe" to
have a version string. The generated AssemblyInfo-Custom.cs is not
commited.

On Aug 19, 4:10 am, Ido Ran  wrote:
> Hi,
> I'm using git to manage my .NET solution which contain 4 C# projects.
> .NET assemblies have version of schema major.minor.build.revision.
> I manage the major and minor manually.
>
> I would like to hook git into my help by increasing the build number
> of each project that is part of this commit.
>
> I think I can use git hooks (pre-commit) to run an MSBuild task that
> will change the version of the assembly or any other command line to
> change the version of the assembly.
>
> I would like to know if anyone does something like this?
>
> Thank you,
> Ido

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To post to this group, send email to git-us...@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.



[git-users] Re: Clone Shows Old Moved Files

2010-08-31 Thread Konstantin Khomoutov
On Aug 30, 2:16 pm, Gregg Leichtman  wrote:

>  From my CVS experience, I would expect the behavior that I have seen. I
> just forgot to do the commit and it didn't click that I missed the
> commit until I was told that it does work as I originally expected it
> should.
[...]
>> in fact git-mv (like git-add and git-rm) opperates just on working
>> directory and staging area (index) levels. It doesn't touch git
>> repository itself. So it

I tend to think Git only automatically records a commit when it's the
most sensible thing to do from the point of view of commit
"atomicity". Let me explain.
Take merging for example -- a merge which does not result in fast-
forward and does not fail due to conflicts is an atomic operation
since you hardly ever need to amend the commit resulting from a
successfull merge, and so the commit is done automatically (but you
can override this behaviour using --no-commit and introduce any
changes you want before committing).
Renaming a file, on the other hand, is quite an opposite kind of
operation: you might want to include several renames in your commit,
or you may wish to rename a file and then change it, and commit all
these changes at once. Or you might even want to modify a file, rename
it and then modify it again (using its new name).
Renaming a file is similar to editing a file in this regard: you just
modify a filesystem object.

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To post to this group, send email to git-us...@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.



[git-users] 42% Chrome ore 1000 m/ton lot c&f cheep price

2010-08-31 Thread iqbal iqbal
42% Chrome ore 1000 m/ton lot c&f cheep price
http://buy-sell-pakistani-minerals.blogspot.com

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To post to this group, send email to git-us...@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.



Re: [git-users] Re: git commit not doing anything

2010-08-31 Thread E.J. Hassick
Is this just happening in a specific project of yours or in others too?

On Tue, Aug 31, 2010 at 9:13 AM, David Doria  wrote:

> Yep, I tried that too (though it should be equivalent to the
> git add .
> git commit
>
> that I've been trying.
>
> I even tried
>
> git commit -v -m "test commit"
>
> and nothing is displayed (even with the verbose output!)
>
> This is driving me crazy... any more thoughts?
>
> On Aug 31, 1:09 am, iñigo medina  wrote:
> > Hi David,
> >
> > did you try with git commit -a?
> >
> > iñ
> >
> >
> >
> > > I have some staged files:
> >
> > > [dor...@localhost VTK-GraphColors]$ git status
> > > # On branch VTK-GraphColors
> > > # Changes to be committed:
> > > # (use "git reset HEAD ..." to unstage)
> > > #
> > > # modified: Infovis/vtkApplyColors.cxx
> > > # modified: Infovis/vtkApplyColors.h
> > > # modified: Views/vtkRenderedGraphRepresentation.cxx
> > > # modified: Views/vtkRenderedGraphRepresentation.h
> >
> > > but when I try to commit:
> >
> > > [dor...@localhost VTK-GraphColors]$ git commit -m "ENH: allow
> > > passthrough coloring"
> >
> > > nothing happens. There are no errors, it simply doesn't commit the
> > > files. Any clues?
> >
> > > Thanks,
> >
> > > David
> >
> > > --
> > > You received this message because you are subscribed to the Google
> Groups
> >
> > "Git for human beings" group.> To post to this group, send email to
> git-us...@googlegroups.com.
> > > To unsubscribe from this group, send email to
> >
> > git-users+unsubscr...@googlegroups.com
> 
> > .> For more options, visit this group at
> >
> > http://groups.google.com/group/git-users?hl=en.
> >
> >
> >
> >
>
> --
> You received this message because you are subscribed to the Google Groups
> "Git for human beings" group.
> To post to this group, send email to git-us...@googlegroups.com.
> To unsubscribe from this group, send email to
> git-users+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/git-users?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To post to this group, send email to git-us...@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.



[git-users] Re: git commit not doing anything

2010-08-31 Thread David Doria
Yep, I tried that too (though it should be equivalent to the
git add .
git commit

that I've been trying.

I even tried

git commit -v -m "test commit"

and nothing is displayed (even with the verbose output!)

This is driving me crazy... any more thoughts?

On Aug 31, 1:09 am, iñigo medina  wrote:
> Hi David,
>
> did you try with git commit -a?
>
> iñ
>
>
>
> > I have some staged files:
>
> > [dor...@localhost VTK-GraphColors]$ git status
> > # On branch VTK-GraphColors
> > # Changes to be committed:
> > # (use "git reset HEAD ..." to unstage)
> > #
> > # modified: Infovis/vtkApplyColors.cxx
> > # modified: Infovis/vtkApplyColors.h
> > # modified: Views/vtkRenderedGraphRepresentation.cxx
> > # modified: Views/vtkRenderedGraphRepresentation.h
>
> > but when I try to commit:
>
> > [dor...@localhost VTK-GraphColors]$ git commit -m "ENH: allow
> > passthrough coloring"
>
> > nothing happens. There are no errors, it simply doesn't commit the
> > files. Any clues?
>
> > Thanks,
>
> > David
>
> > --
> > You received this message because you are subscribed to the Google Groups
>
> "Git for human beings" group.> To post to this group, send email to 
> git-us...@googlegroups.com.
> > To unsubscribe from this group, send email to
>
> git-users+unsubscr...@googlegroups.com .com>
> .> For more options, visit this group at
>
> http://groups.google.com/group/git-users?hl=en.
>
>
>
>

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To post to this group, send email to git-us...@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.