netreg-devel: more updates to /opt/netreg/stable/netdb/lib/CMU/Netdb/auth.pm

[Frank Sweetser]

What I would suggest is that you first get a working install with what's
currently in git, and then get your changes working in a separate branch of
your own creation.  That'll keep all of your local work nicely bundled up
together, while still letting you pull down and merge any upstream changes.
Once you've got your local branch with the active directory code set up, we
can look at merging it back upstream.  If it can coexist nicely with people
who aren't using active directory, I think it would be a great feature to
merge in.

If none of that made sense, try reading through a couple of git tutorials, and
it should become a lot clearer.

Frank Sweetser fs at wpi.edu    |  For every problem, there is a solution that
Manager of Network Operations   |  is simple, elegant, and wrong.
Worcester Polytechnic Institute |           - HL Mencken

On 03/22/2012 12:03 PM, apg at eecs.wsu.edu wrote:
> Ok. Now that I've a working port to Centos 6, I'm going to try a fresh
> install from git, and then add in the code that Dave Nolan added to populate
> users from Active Directory. That is, if you want that code added to the git
> repo?
> 
> -al
> 
>  
> 
> On Thu, Mar 22, 2012 at 10:44:53AM -0400, Frank Sweetser wrote:
>> On 03/21/2012 06:15 PM, apg at eecs.wsu.edu wrote:
>>> On Wed, Mar 21, 2012 at 01:50:48PM -0400, Frank Sweetser wrote:
>>>>
>>>> Okay, I think that all of these changes are either already in github, or have
>>>> now been added in.
>>>>
>>>> On a related note, would you mind either using git format-patch to generate
>>>> these diffs, or at least generated unified diffs with the -u option to diff?
>>>> They make it much easier to read and integrate.
>>>
>>>
>>> Ok, will do. I've managed to tap-dance my way around using any CVS... 
>>>
>>> doing this:
>>> git format-patch -a a.pl a.fix.pl 
>>>
>>> I get this:
>>> fatal: Not a git repository (or any of the parent directories): .git
>>>
>>> soooo, I'm assuming I have to add it to some git repo, or something?
>>
>> The git magic will only work in a source tree that's actually a checked out
>> copy of a git repo.  github has a decent getting started tutorial:
>>
>> http://help.github.com/
>>
>> Eventually switching over to a development system working out of github will
>> also ensure that you're working on the latest code, and don't need to worry
>> about duplicating any work.
>>
>> In the short term, though, since that's a larger project, just using the -u
>> flag to diff to generate the patches will help a lot.
>>
>> -- 
>> Frank Sweetser fs at wpi.edu    |  For every problem, there is a solution that
>> Manager of Network Operations   |  is simple, elegant, and wrong.
>> Worcester Polytechnic Institute |           - HL Mencken
> 
> 
> 
> Thanks!
> 
> 
> -al
> 
> keepalived
> 
> 
> ---------------------------------------------------------------
>  Allen P. Guyer
>  Unix Systems Administrator
> 
>  School of Electrical Engineering & Computer Science
>  Washington State University
> 
> ==============================================================================
> ...probability factor of one to one
> ...we have normality, I repeat we have normality.
> ==============================================================================
> 
> 
> 
> 
> 
> 
> 
> 
> 
>