New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sc is looking for a new maintainer #18
Comments
@n-t-roff I'd be very pleased to take over this role. |
@ other users: Are there any objections? |
Hmm, when I have a look at your GitHub account I get the impression that you do or did not do a lot of C or Unix tool development? Would it not be better to live with pull requests for the time being? |
Indeed, I'm not a C coding expert, so if Maintainer means main C developper of the project, my profile don't match this requirement :-) |
Yes, expert C and Nevertheless quality pull requests are always possible and applied short-term. So you need not to worry regarding the BlackBerry software suite integration. |
just found this project... I used vc on Unix Sys V r2.1 back in the (19)80s at Bell Labs... I don't have a ton of time, but assuming it's mostly mature I'm willing to assist maintaining it. |
You really had worked at bell labs... sounds interesting. |
ya .. I worked there 1986-2002 .. they finally figured out that the 1982
Divestiture ruling was going to bankrupt them :P
if you're interested in the history...
https://www.historyfactory.com/insights/this-month-in-business-history-bell-system/
in 2007 Stephen Colbert did a bit explaining how Cingular became AT&T
Wireless after AT&T's breakup and subsequent mega-mergers. pretty funny if
you can find it
…On Tue, Jul 26, 2022 at 9:01 AM n-t-roff ***@***.***> wrote:
You really had worked at bell labs... sounds interesting.
I have invited you as contributor, normally you should have full access
rights to the repository with it.
—
Reply to this email directly, view it on GitHub
<#18 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADVJRKCCBLHXFFEPG3OBI3TVV74THANCNFSM4KYV3MFQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Interesting indeed. Thank you for the information. |
greets .. this is an attempt to fix issue #6 (thought I'd start w/ the
easy one)
I don't want to screw things up w/ my first commit :P
Do you want to try this patch and see how it fairs? (I only tested on Mac
OSX) .. I can test on several flavors of Linux when I get home (currently
on a business trip)
my test:
./configure;make # verify still works in current dir
make clobber; # new target, destroy all built files
mkdir ../sc_build;cd ../sc_build; ../sc/configure; make
make clobber;
if you think it looks ok, I'll commit/push/close issue
…On Wed, Jul 27, 2022 at 8:11 AM n-t-roff ***@***.***> wrote:
Interesting indeed. Thank you for the information.
—
Reply to this email directly, view it on GitHub
<#18 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADVJRKHW5ALIRCA6FXGJ3PTVWE7PVANCNFSM4KYV3MFQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
oops .. I didn't realize I've been replying to this thread the whole time. sorry about that |
Thank you. I did extensive tests on the BSDs and Solaris in the past. I'm not quite sure but I believe the build tool chain had completely been POSIX. The patch looks a little bit GNU dependent. Hopefully we don't break compatibility with systems which have POSIX only tools (e.g. some BSDs). Maybe you could try to commit it and rollback if there are complaints from non-GNU systems. We should continue the discussion in #6. |
Since I don't have the time to maintain GitHub projects any more,
sc
could be transferred to a new owner which continues maintenance.The text was updated successfully, but these errors were encountered: