Re: [git-users] git-filter-branch : How to filter all commits from an given commit ?

2014-10-27 Thread Alcolo Alcolo

My question is how can I do and you answer is why you do this.

My main question is:
git-filter-branch allow to select commits to filter. How can I select all 
commits from a given commit C, including C?
This question can be declined for git-rev-list.

This question has no meaning ??

I can do the job with git filter-branch -- --all, but this will takes hours 
to change only ~50 last commits.
I just want to know how this can be optimized.


Le vendredi 24 octobre 2014 22:32:39 UTC+2, Dale Worley a écrit :

 Actually, git-filter-branch is based on git-rev-list etc. 

The purpose of git-filter-branch, though, is to be able to apply a 
 complicated transformation to every commit in the branch, usually the 
 uniform removal of particular paths from the file tree.

No, changing commit date or authors is not a complicated transformation.
 

  What you seem 
 to be wanting to do is modify a commit (although I'm not clear whether 
 you simply want to change the meta-data or whether you want to also 
 change the file content), and then have that propagated through all of 
 the descendant commits (at least in their hashes, and possibly in 
 their file content).

(I want changing something in one commit object: meta-data, that's can 
include change of tree-id: file contents (changing tree-id is not my goal)) 

  That job isn't really the purpose of 
 git-filter-branch, because in what you want, the changes to the 
 descendant commits are only due to propagatation from the changes in 
 C. 

Yes it is: since git-filter-branch is the only way to integrate git-replace 
or grafts changes definitively,
git-filter-branch purpose is to rehash commits.
 


 But why are you, of all people, asking about this?  You've used 
 git-rebase--merge-safe, which does this sort of task.  You've even 
 *improved* it. 

git-rebase--merge-safe:
- it rehash commits: git-filter-branch jobs
- it merge changes like git rebase, it is its main goal: but I don't need 
this, it's not my goal.


 Dale 


-- 
You received this message because you are subscribed to the Google Groups Git 
for human beings group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [git-users] Git objects and user permissions

2014-10-27 Thread Dale R. Worley
 From: Jon Zeolla zeo...@gmail.com

 Nevermind I guess the sticky bit trickles down throughout the whole 
 directory structure.  

Strictly speaking, the default value of the sticky bit when a
directory is created is the sticky bit value of its parent directory.
It trickles down when the directories are created.

Dale

-- 
You received this message because you are subscribed to the Google Groups Git 
for human beings group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.