Re: git remote rename, why dosen't it exists?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 2008-06-03 at 21:12 +0100, Johannes Schindelin wrote:
> Hi,
> 
> [please do not top-post: it makes it very hard to follow the flow, 
> especially on a high-volume mailing list like this.]
> 
sorry about that. :-/ 

> On Tue, 3 Jun 2008, Victor Bogado da Silva Lins wrote:
> 
> > On Tue, 2008-06-03 at 14:49 +0100, Johannes Schindelin wrote:
> > 
> > > On Tue, 3 Jun 2008, Victor Bogado da Silva Lins wrote:
> > > 
> > > > Well, that's about it, I need to rename my remotes. Mainly to move 
> > > > the origin to another repository and I miss the feature. Since many 
> > > > time there is a reason for a missing feature, I fought that maybe I 
> > > > should ask here, before nosing around the sources... :)
> > > 
> > > The reason is easy to find: nobody cared enough about this feature to 
> > > implement it.
> > > 
> > > Just tell me if you want to do it, I'll provide you with the necessary 
> > > details.
> >
> > I don't mind trying. :P Pointers would help me, I already found that the
> > git-remote source is on the file builtin-remote.c, bu I have not yet
> > found the main function of it.
> 
> There is no main function, since it is a builtin.  The "main" function is 
> called cmd_remote().
> 
> You might find inspiration with the rm() function, or might even be able 
> to refactor the rm() function into an rm(), and an rm_or_rename() which
> does both rm() and rename() depending on a second parameter being NULL or 
> not.

I trying to refactor rm into rm_or_rename, but I stumbled into a
problem, how do I free a remote struct obtained with "remote_get"?
Another possibility would be another way to check if a remote already
exists without allocating it in case it does. The need comes from
testing whether the destination name already exists, if it does exists I
must free the remote_get and bail_out. 

--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux